home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.5 KB | 33 lines | [TEXT/GEOL] |
- Item 6528361 4-April-88 13:11
-
- From: SHEETS1 Sheets, Steve
-
- To: MACAPP$ MacApp Interest List
-
- Sub: Saving Resource Data
-
- Dear MacAppers,
- I am having a problem trying to read/write a document using MacApp. My
- document contains no information in the data fork, and a single variable size
- resource in the resource fork. Exactly how does resource saving work under
- MacApp?
- I examined the example, DrawShape, because it was the only one that handle
- this type of thing. According to it, DoRead just needs to load in the resource
- and copy the data (simple). DoRead does not need to release the resource, does
- the system do this? DoWrite was much more puzzling. It creates a new handle,
- stuffs the data into it, and then adds the handles as a resource to the file.
- What happen to the old resource if there was any? Again there is no releasing
- of the resource, there is not even any flushing of the resource to make sure
- the write was sent to the file. Does MacApp handle all this?
- By the way, what are the constants kRsrcTypeOverhead and kRsrcOverhead?
- DrawShape had them as something that needed to be added to the rsrcForkBytes
- parameter of DoNeedDiskSpace. Are they the overhead involved in added a
- resource fork to a file? What happens if more than one resource and/or more
- than one type of resource is added, how is rsrcForkBytes calculated?
- I am about to dive into the MacApp source code, but any hints would be
- helpful and time saving!
-
- Steve Sheets
-
-
-